Flight tag obtaining method, terminal, and server

ABSTRACT

This application discloses a flight tag obtaining method, terminal, and server. A takeoff geographic location of a first unmanned aerial vehicle can be obtained when the first unmanned aerial vehicle takes off. The takeoff geographic location of the first unmanned aerial vehicle can then be sent to a server. A flight tag returned by the server can be obtained. The flight tag can indicate whether another aerial vehicle took off from the takeoff geographic location of the first unmanned aerial vehicle before the first unmanned aerial vehicle.

RELATED APPLICATION

This application is a continuation of International Application No.PCT/CN2017/078805, filed on Mar. 30, 2017, which claims priority toChinese Patent Application No. 201610203591.1, entitled “FLIGHT TAGOBTAINING METHOD, TERMINAL, AND SERVER”, filed with the Chinese PatentOffice on Apr. 1, 2016. The entire disclosures of the prior applicationsare hereby incorporated by reference in their entirety.

FIELD OF THE TECHNOLOGY

This application relates to a flight tag obtaining method, terminal, andserver.

BACKGROUND OF THE DISCLOSURE

Currently, an existing unmanned aerial vehicle usually stores flightdata in the unmanned aerial vehicle. The flight data is used forrecording a flight parameter in a flying process or tracking a flightfault, and is used by the unmanned aerial vehicle itself. However, whensuch a manner is used, flight records of another unmanned aerial vehiclecannot be learned due to a lack of interaction. Consequently, flightdata of unmanned aerial vehicles cannot be shared, and flight data of aplurality of unmanned aerial vehicles cannot be processed. For example,competition, learning, emulation, collection of the flight data, and thelike cannot be performed between the plurality of unmanned aerialvehicles.

For the foregoing problem, at present, no effective solution has beenproposed.

SUMMARY

Embodiments of this application provide a flight tag obtaining method,terminal, and server, to at least resolve a technical problem that aflight tag of an unmanned aerial vehicle cannot be obtained by using theexisting technology.

According to an aspect of an embodiment of this application, there isprovided a non-transitory computer-readable medium storing instructionswhich when executed by at least one processor cause the at least oneprocessor to perform operations that can include obtaining a takeoffgeographic location of a first unmanned aerial vehicle when the firstunmanned aerial vehicle takes off. The takeoff geographic location ofthe first unmanned aerial vehicle is sent to a server. A flight tagreturned by the server is obtained. The flight tag indicates whetheranother unmanned aerial vehicle took off from the takeoff geographiclocation of the first unmanned aerial vehicle before the first unmannedaerial vehicle.

According to another aspect of an embodiment of this application, amethod is further provided. A takeoff geographic location of a firstunmanned aerial vehicle is received by a server from an informationprocessing apparatus when the first unmanned aerial vehicle takes off. Adetermination is made by the server as to whether the received takeoffgeographic location of the first unmanned aerial vehicle is included ina plurality of stored takeoff geographic locations. When the takeoffgeographic location of the first unmanned aerial vehicle is included inthe stored takeoff geographic locations, a first flight tag is sent bythe server to the information processing apparatus. The first flight tagindicates that another unmanned aerial vehicle took off from the takeofflocation of the first unmanned aerial vehicle before the first unmannedaerial vehicle. When the takeoff geographic location of the firstunmanned aerial vehicle is not included in the stored takeoff geographiclocations, a second flight tag is sent by the server to the informationprocessing apparatus. The second flight tag indicates that anotherunmanned aerial vehicle has not taken off from the takeoff location ofthe first unmanned aerial vehicle before the first unmanned aerialvehicle.

According to still another aspect of an embodiment of this application,an information processing apparatus is further provided. Processingcircuitry of the terminal obtains a takeoff geographic location of afirst unmanned aerial vehicle when the first unmanned aerial vehicletakes off. The processing circuitry sends the takeoff geographiclocation of the first unmanned aerial vehicle to a server. Theprocessing circuitry further obtains a flight tag returned by theserver. The flight tag indicates whether another unmanned aerial vehicletook off from the takeoff geographic location of the first unmannedaerial vehicle before the first unmanned aerial vehicle.

According to still another aspect of an embodiment of this application,an apparatus is further provided. Processing circuitry of the apparatusreceives a takeoff geographic location of a first unmanned aerialvehicle from an information processing apparatus when the first unmannedaerial vehicle takes off. The processing circuitry determines whetherthe received takeoff geographic location of the first unmanned aerialvehicle is included in a plurality of stored takeoff geographiclocations. When the takeoff geographic location of the first unmannedaerial vehicle is included in the stored takeoff geographic locations,the processing circuitry sends a first flight tag to the informationprocessing apparatus. The first flight tag indicates that anotherunmanned aerial vehicle took off from the takeoff geographic location ofthe first unmanned aerial vehicle before the first unmanned aerialvehicle. When the takeoff geographic location of the first unmannedaerial vehicle is not included in the stored takeoff geographiclocations, the processing circuitry sends a second flight tag to theinformation processing apparatus. The second flight tag indicates thatanother unmanned aerial vehicle has not taken off from the takeoffgeographic location of the first unmanned aerial vehicle before thefirst unmanned aerial vehicle.

In embodiments of this application, a client running on an informationprocessing apparatus obtains a takeoff geographic location of a firstunmanned aerial vehicle when the first unmanned aerial vehicle takesoff. The client sends the takeoff geographic location to a server; andobtains a flight tag returned by the server. The flight tag is used forindicating whether the first unmanned aerial vehicle is an unmannedaerial vehicle first taking off from the takeoff geographic location ofthe first unmanned aerial vehicle. The takeoff geographic locationobtained when the unmanned aerial vehicle takes off is sent to theserver, so that the server establishes a common database of unmannedaerial vehicles on the server by using the obtained takeoff geographiclocation of the unmanned aerial vehicle. Further, the database is usedfor establishing interaction between the client running on the controlterminal and the server, to implement sharing of the takeoff geographiclocation of the unmanned aerial vehicle, and return a flight tagcorresponding to the unmanned aerial vehicle to the control terminalaccording to the takeoff geographic location of the unmanned aerialvehicle. Therefore, the technical problem that a flight tag of anunmanned aerial vehicle cannot be obtained by using the existingtechnology is resolved, to implement sharing of the foregoing flight tagof the unmanned aerial vehicle in social space of the client.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings described herein are used for providing afurther understanding of this application, and form part of thisapplication. Exemplary embodiments of this application and descriptionsthereof are used for explaining this application, and do not constituteany inappropriate limitation to this application. In the figures:

FIG. 1 is a schematic diagram of an application environment of anoptional flight tag obtaining method according to an embodiment of thisapplication;

FIG. 2 is a flowchart of an optional flight tag obtaining methodaccording to an embodiment of this application;

FIG. 3 is a schematic diagram of an optional flight tag obtaining methodaccording to an embodiment of this application;

FIG. 4 is a schematic diagram of another optional flight tag obtainingmethod according to an embodiment of this application;

FIG. 5 is a flowchart of another optional flight tag obtaining methodaccording to an embodiment of this application;

FIG. 6 is a schematic diagram of still another optional flight tagobtaining method according to an embodiment of this application;

FIG. 7 is a flowchart of still another optional flight tag obtainingmethod according to an embodiment of this application;

FIG. 8 is a schematic diagram of an optional flight tag obtainingterminal according to an embodiment of this application;

FIG. 9 is a schematic diagram of an optional flight tag obtaining serveraccording to an embodiment of this application;

FIG. 10 is a schematic structural diagram of an optional flight tagobtaining terminal according to an embodiment of this application; and

FIG. 11 is a schematic structural diagram of an optional flight tagobtaining server according to an embodiment of this application.

DESCRIPTION OF EMBODIMENTS

To make persons skilled in the art understand the solutions in thisapplication better, the following clearly and completely describes thetechnical solutions in the embodiments of this application withreference to the accompanying drawings in the embodiments of thisapplication. The described embodiments are merely some but not all ofthe embodiments of this application. All other embodiments obtained bypersons of ordinary skill in the art based on the embodiments of thisapplication shall fall within the protection scope of this application.

It should be noted that, in the specification, claims, and accompanyingdrawings of this application, the terms “first”, “second”, and so on areintended to distinguish between similar objects rather than describe aspecific order. It should be understood that, the terms used in this wayis exchangeable in a proper case, so that the embodiments describedherein of this application can be implemented in another order exceptthose shown or described herein. Moreover, the terms “include”,“contain” and any other variants mean to cover the non-exclusiveinclusion, for example, a process, method, system, product, or devicethat includes a list of steps or units is not necessarily limited tothose steps and units, but may include other steps or units notexpressly listed or inherent to such a process, method, product, ordevice.

Embodiment 1

According to this embodiment of this application, a flight tag obtainingmethod is provided. The flight tag obtaining method may be applied to,but not limited to, an application environment shown in FIG. 1. Acontrol terminal 104 obtains a takeoff geographic location of a firstunmanned aerial vehicle (a unmanned aerial vehicle 102 as shown inFIG. 1) when the first unmanned aerial vehicle takes off, sends thetakeoff geographic location to a server 106, and obtains a flight tagreturned by the server 106, the flight tag being used for indicatingwhether the first unmanned aerial vehicle (the unmanned aerial vehicle102 as shown in FIG. 1) is an unmanned aerial vehicle first taking offfrom the takeoff geographic location of the first unmanned aerialvehicle (the unmanned aerial vehicle 102 as shown in FIG. 1). Flightdata (for example, the takeoff geographic location) of the unmannedaerial vehicle is sent to the server, to establish a common database ofunmanned aerial vehicles on the server, to use the database to returnthe flight tag of the unmanned aerial vehicle to the control terminal,and further implement sharing of the foregoing flight tag of theunmanned aerial vehicle in social space (e.g., an online social spacesuch as a social media network).

Optionally, in this embodiment, the foregoing control terminal mayinclude but is not limited to at least one of the following: a mobileterminal, a wrist worn smart device, or a game controller. The mobileterminal may include but is not limited to at least one of thefollowing: a mobile phone, a tablet computer, or a laptop computer. Theforegoing is merely exemplary, and no limitation is set in thisembodiment.

Optionally, in this embodiment, the foregoing terminal may, but notlimited to, use a network to interact with the server. The foregoingnetwork may include but is not limited to at least one of the following:a wide area network, a metropolitan area network, or a local areanetwork. The foregoing terminal may, but not limited to, use wirelessconnection to perform data interaction with the unmanned aerial vehicle.The foregoing wireless connection may include but is not limited to atleast one of the following: Bluetooth or WiFi. The foregoing is merelyexemplary, and no limitation is set in this embodiment.

According to an embodiment of this application, a flight tag obtainingmethod is provided. As shown in FIG. 2, the method includes:

S202: Obtain a takeoff geographic location of a first unmanned aerialvehicle when the first unmanned aerial vehicle takes off.

S204: Send the takeoff geographic location of the first unmanned aerialvehicle to a server.

S206: Obtain a flight tag returned by the server, the flight tag beingused for indicating whether the first unmanned aerial vehicle is anunmanned aerial vehicle first taking off from the takeoff geographiclocation of the first unmanned aerial vehicle.

Optionally, in this embodiment, the foregoing flight tag obtainingmethod may be applied to, but not limited to, a process in which aclient running on a control terminal obtains a flight tag of an unmannedaerial vehicle. The foregoing client running on the control terminal isconfigured to control takeoff of the unmanned aerial vehicle. Forexample, after an obtained takeoff geographic location of a firstunmanned aerial vehicle when the first unmanned aerial vehicle takes offis sent to a server, a flight tag of the first unmanned aerial vehiclereturned by the server is obtained. In addition, as shown in FIG. 3, theflight tags of the unmanned aerial vehicle returned by the server aredisplayed in the client (a user name is ID_01) running on the controlterminal. For example, the flight tags returned by the server include aflight tag_1 and a flight tag_2. For example, the flight tags may be“occupying for a first time” or “flying across”. The foregoing is merelyexemplary, and no limitation is set in this embodiment.

It should be noted that, in this embodiment, a client running on acontrol terminal obtains a takeoff geographic location of a firstunmanned aerial vehicle when the first unmanned aerial vehicle takesoff; sends the takeoff geographic location to a server; and obtains aflight tag returned by the server, the flight tag being used forindicating whether the first unmanned aerial vehicle is an unmannedaerial vehicle first taking off from the takeoff geographic location ofthe first unmanned aerial vehicle. The takeoff geographic locationobtained when the unmanned aerial vehicle takes off is sent to theserver, so that the server establishes a common database of unmannedaerial vehicles on the server by using the obtained takeoff geographiclocation of the unmanned aerial vehicle. Further, the database is usedfor establishing interaction between the client running on the controlterminal and the server, to implement sharing of the takeoff geographiclocation of the unmanned aerial vehicle, and return a flight tagcorresponding to the unmanned aerial vehicle to the control terminalaccording to the takeoff geographic location of the unmanned aerialvehicle. Therefore, the foregoing flight tag of the unmanned aerialvehicle can be shared in social space of the client.

Optionally, in this embodiment, after the sending the takeoff geographiclocation of the first unmanned aerial vehicle to a server, and beforethe obtaining a flight tag returned by the server, the method furtherincludes: determining, by the server, whether there is a takeoffgeographic location in stored takeoff geographic locations that is thesame as the received takeoff geographic location of the first unmannedaerial vehicle; and sending a corresponding flight tag according to adetermining result. The flight tag may include but is not limited to atleast one of the following: a first flight tag used for indicating thatthe first unmanned aerial vehicle is not an unmanned aerial vehiclefirst taking off from the takeoff geographic location of the firstunmanned aerial vehicle, or a second flight tag used for indicating thatthe first unmanned aerial vehicle is an unmanned aerial vehicle firsttaking off from the takeoff geographic location of the first unmannedaerial vehicle.

Optionally, in this embodiment, the foregoing flight tag may further beused for, but not limited to, indicating at least one of the following:a geographic name corresponding to the takeoff geographic location ofthe first unmanned aerial vehicle, a takeoff date of the first unmannedaerial vehicle, or a takeoff time of the first unmanned aerial vehicle.For example, a first unmanned aerial vehicle is controlled by a client(a user name is ID_01) running on a control terminal. After the firstunmanned aerial vehicle flies for a plurality of times, obtained flighttags displayed in the client may be shown in FIG. 4. Takeoff geographiclocations included in a first flight tag (represented by using“occupying for a first time”) are as follows: “Eiffel Tower, France(Sep. 24, 2015)”, “Madrid, Spain (Jul. 17, 2015)”, “Hokkaido, Japan(Jun. 4, 2015)”, and “Paradise Island, the Maldives (Apr. 30, 2015)”.Takeoff geographic locations included in a second flight tag(represented by using “flying across”) are as follows: “Triumphal arch,France (Sep. 23, 2015)”, “Barcelona, Spain (Jul. 19, 2015)”, and “Tokyo,Japan (Jun. 6, 2015)”.

Optionally, in this embodiment, the takeoff geographic location of theforegoing first unmanned aerial vehicle may include but is not limitedto one of the following: 1) a geographic location of the first unmannedaerial vehicle when the first unmanned aerial vehicle takes off; or 2) ageographic location of the control terminal when the first unmannedaerial vehicle takes off. When the takeoff geographic location of thefirst unmanned aerial vehicle is the geographic location of the firstunmanned aerial vehicle when the first unmanned aerial vehicle takesoff, the takeoff geographic location may be obtained in, but is notlimited to, at least one of the following manners: 1) The controlterminal obtains the geographic location of the first unmanned aerialvehicle collected by the first unmanned aerial vehicle when the firstunmanned aerial vehicle takes off; or 2) The control terminal obtains,by detection, the geographic location of the first unmanned aerialvehicle when the first unmanned aerial vehicle takes off.

Optionally, in this embodiment, the sending the takeoff geographiclocation of the first unmanned aerial vehicle to a server includes oneof the following:

1) when the first unmanned aerial vehicle takes off, sending the takeoffgeographic location of the first unmanned aerial vehicle to the server;or

2) after the first unmanned aerial vehicle takes off, sending thetakeoff geographic location of the first unmanned aerial vehicle to theserver.

It should be noted that, in manner 1) of this embodiment, the takeoffgeographic location of the first unmanned aerial vehicle is sent to theserver in real time when the first unmanned aerial vehicle takes off, sothat the server can implement real-time comparison and real-timefeedback, to ensure that the client running on the control terminal canobtain in time the flight tag matched to the first unmanned aerialvehicle, and the social space of the client can update and display theobtained flight tag in real time. Further, data recorded in the databaseof the server can further be updated in real time, to ensure theaccuracy and update efficiency of the database, so that a plurality ofusers can invoke the data in the database at the same time, to implementthe feasibility of multi-user interaction.

In addition, in manner 2) of this embodiment, the takeoff geographiclocation of the first unmanned aerial vehicle may alternatively be sentto the server after the first unmanned aerial vehicle takes off, so thatthe server is synchronized with the obtained takeoff geographic locationof the first unmanned aerial vehicle after a time interval. Asynchronization process in which the takeoff geographic location of thefirst unmanned aerial vehicle is sent to the server is separated, thatis, a plurality of takeoff geographic locations obtained at particulartime intervals is sent to the server together, to reduce a number ofsending operations, and therefore improve the efficiency of sending thetakeoff geographic locations to the server.

Optionally, in this embodiment, after the first unmanned aerial vehicletakes off, sending the takeoff geographic location of the first unmannedaerial vehicle to the server in manner 2) includes one of the following:

(1) after the first unmanned aerial vehicle takes off, obtaining asending instruction, and sending, in response to the sendinginstruction, the takeoff geographic location of the first unmannedaerial vehicle to the server; or

(2) after the first unmanned aerial vehicle takes off, determiningwhether a preset sending moment is reached, and when it is determinedthat the sending moment is reached, sending the takeoff geographiclocation of the first unmanned aerial vehicle to the server.

That is, after the first unmanned aerial vehicle takes off, the takeoffgeographic location of the first unmanned aerial vehicle may be sent tothe server in response to the obtained sending instruction, or theobtained takeoff geographic location of the first unmanned aerialvehicle may be sent to the server at the preset sending moment.

It should be noted that, in this embodiment, the foregoing sendinginstruction may be but is not limited to a sending instruction triggeredby a user by means of an input operation. The input operation mayinclude but is not limited to at least one of the following: clicking apredetermined trigger button, collecting predetermined voice, orobtaining a predetermined motion sensing gesture (or motion gesture).

In addition, in this embodiment, the foregoing preset sending moment mayinclude but is not limited to at least one of the following: a momentsatisfying a predetermined condition, or a preset cycle end moment. Forexample, the predetermined condition may be detecting a preconfigurednetwork signal, such as a 4G network signal or a WiFi signal.

Specifically, descriptions are provided with reference to the followingexamples. As shown in FIG. 5, in the example, that a geographic locationof a first unmanned aerial vehicle when the first unmanned aerialvehicle takes off is a takeoff geographic location of the first unmannedaerial vehicle is used as an example.

S502: A client 504 running on a control terminal obtains a geographiclocation of a first unmanned aerial vehicle collected by the firstunmanned aerial vehicle 502 when the first unmanned aerial vehicle takesoff.

S504: The client 504 running on the control terminal sends the takeoffgeographic location of the first unmanned aerial vehicle to a server506.

S506: The server 506 determines whether there is a takeoff geographiclocation in stored takeoff geographic locations that is the same as thereceived takeoff geographic location of the first unmanned aerialvehicle; and obtains a corresponding flight tag according to adetermining result.

S508: The server 506 returns the flight tag to the client 504 running onthe control terminal.

S510: The client 504 running on the control terminal displays the flighttag.

According to the embodiment provided in this application, the takeoffgeographic location obtained when the unmanned aerial vehicle takes offis sent to the server, so that the server establishes a common databaseof unmanned aerial vehicles on the server by using the obtained takeoffgeographic location of the unmanned aerial vehicle. Further, thedatabase is used for establishing interaction between the client runningon the control terminal and the server, to implement sharing of thetakeoff geographic location of the unmanned aerial vehicle, and returnthe flight tag corresponding to the unmanned aerial vehicle to thecontrol terminal according to the takeoff geographic location of theunmanned aerial vehicle. Therefore, the foregoing flight tag of theunmanned aerial vehicle can be shared in social space of the client, toresolve a technical problem that a flight tag of an unmanned aerialvehicle cannot be obtained by using the existing technology.

In an optional solution, the sending the takeoff geographic location ofthe first unmanned aerial vehicle to a server includes one of thefollowing:

1) when the first unmanned aerial vehicle takes off, sending the takeoffgeographic location of the first unmanned aerial vehicle to the server;or

2) after the first unmanned aerial vehicle takes off, sending thetakeoff geographic location of the first unmanned aerial vehicle to theserver.

It should be noted that, in this embodiment, the takeoff geographiclocation of the first unmanned aerial vehicle may be sent to the serverwhen the first unmanned aerial vehicle takes off or after the firstunmanned aerial vehicle takes off. That is, the takeoff geographiclocation may be sent to the server in real time, so that the server canimplement real-time comparison and real-time feedback, to ensure thatthe client running on the control terminal can obtain in time the flighttag matched the first unmanned aerial vehicle, and the social space ofthe client can update and display the obtained flight tag in real time.Alternatively, the synchronization process may be separated, to firststore a plurality of takeoff geographic locations obtained at particulartime intervals, and then send the obtained takeoff geographic locationsto the server together, to reduce a number of sending operations, andimprove the efficiency of sending the takeoff geographic location to theserver.

Optionally, in this embodiment, in manner 2), the foregoing takeoffgeographic location of the first unmanned aerial vehicle may be firststored in the control terminal, or may be stored in another third-partystorage medium. No limitation is set thereto in this embodiment.

According to the embodiment provided in this application, the takeoffgeographic location of the first unmanned aerial vehicle is sent whenthe first unmanned aerial vehicle takes off or after the first unmannedaerial vehicle takes off, to select different sending moments accordingto different application scenarios, to ensure that the flight tagcorresponding to the takeoff geographic location can be accuratelyobtained in time.

In an optional solution, the after the first unmanned aerial vehicletakes off, sending the takeoff geographic location of the first unmannedaerial vehicle to the server includes one of the following:

1) after the first unmanned aerial vehicle takes off, obtaining asending instruction, and sending, in response to the sendinginstruction, the takeoff geographic location of the first unmannedaerial vehicle to the server; or

2) after the first unmanned aerial vehicle takes off, determiningwhether a preset sending moment is reached, and when it is determinedthat the sending moment is reached, sending the takeoff geographiclocation of the first unmanned aerial vehicle to the server.

Optionally, in this embodiment, after the first unmanned aerial vehicletakes off, the takeoff geographic location of the first unmanned aerialvehicle may be sent to the server in response to the obtained sendinginstruction. The foregoing sending instruction may be but is not limitedto a sending instruction triggered by a user by means of an inputoperation. The input operation may include but is not limited to atleast one of the following: clicking a predetermined trigger button,collecting predetermined voice, or obtaining a predetermined motionsensing gesture. For example, a control interface in which the clientrunning on the control terminal controls the first unmanned aerialvehicle is shown in FIG. 6. The client can control the first unmannedaerial vehicle to perform different operations of “returning andlanding”, “emergent suspension”, and “following mode”, or control thefirst unmanned aerial vehicle to move according to directions indicatedby arrows. In addition, the sending instruction of sending the takeoffgeographic location of the first unmanned aerial vehicle to the servermay alternatively be triggered by using a “control button” after thefirst unmanned aerial vehicle takes off (or when the first unmannedaerial vehicle takes off).

Optionally, in this embodiment, after the first unmanned aerial vehicletakes off, the obtained takeoff geographic location of the firstunmanned aerial vehicle may alternatively be sent to the server at apreset sending moment. The foregoing preset sending moment may includebut is not limited to at least one of the following: a moment satisfyinga predetermined condition, or a preset cycle end moment. For example,the predetermined condition may be detecting a preconfigured networksignal, such as a 4G network signal or a WiFi signal.

According to the embodiment provided in this application, the controlterminal is triggered in different manners to send the takeoffgeographic location of the first unmanned aerial vehicle to the server,to implement operation diversification and facilitate operationsperformed by a user, thereby improving the user experience.

In an optional solution, the obtaining a takeoff geographic location ofa first unmanned aerial vehicle when the first unmanned aerial vehicletakes off includes one of the following:

S1: Obtain a geographic location of the first unmanned aerial vehiclewhen the first unmanned aerial vehicle takes off, the geographiclocation of the first unmanned aerial vehicle being used as the takeoffgeographic location of the first unmanned aerial vehicle; or

S2: Obtain a geographic location of a control terminal when the firstunmanned aerial vehicle takes off, a client running on the controlterminal controlling the takeoff of the first unmanned aerial vehicle;and use the geographic location of the control terminal as the takeoffgeographic location of the first unmanned aerial vehicle.

Optionally, in this embodiment, the geographic location of the firstunmanned aerial vehicle when the first unmanned aerial vehicle takes offmay be obtained in, but is not limited to, at least one of the followingmanners: 1) The control terminal obtains the geographic location of thefirst unmanned aerial vehicle collected by the first unmanned aerialvehicle when the first unmanned aerial vehicle takes off; or 2) Thecontrol terminal obtains, by detection, the geographic location of thefirst unmanned aerial vehicle when the first unmanned aerial vehicletakes off.

According to the embodiment provided in this application, the clientrunning on the control terminal can obtain the takeoff geographiclocation of the first unmanned aerial vehicle collected by the firstunmanned aerial vehicle when the first unmanned aerial vehicle takesoff, or can obtain, by self detection, the takeoff geographic locationof the first unmanned aerial vehicle when the first unmanned aerialvehicle takes off. The takeoff geographic location of the first unmannedaerial vehicle is obtained in different manners, to satisfy actualrequirements of different users, and ensure the accuracy of the obtainedflight tag.

In an optional solution, after the obtaining a flight tag returned bythe server, the method further includes:

S1: Display the flight tag in a client running on a control terminal,the client controlling the takeoff of the first unmanned aerial vehicle,and the flight tag further being used for indicating at least one of thefollowing: a geographic name corresponding to the takeoff geographiclocation of the first unmanned aerial vehicle, a takeoff date of thefirst unmanned aerial vehicle, or a takeoff time of the first unmannedaerial vehicle.

Optionally, in this embodiment, the foregoing flight tag may include butis not limited to at least one of the following: a first flight tag usedfor indicating that the first unmanned aerial vehicle is not an unmannedaerial vehicle first taking off from the takeoff geographic location ofthe first unmanned aerial vehicle, or a second flight tag used forindicating that the first unmanned aerial vehicle is an unmanned aerialvehicle first taking off from the takeoff geographic location of thefirst unmanned aerial vehicle. In addition, the foregoing flight tag mayfurther be but is not limited to being used for indicating at least oneof the following: a geographic name (for example, a location name)corresponding to the takeoff geographic location (for example, alocation coordinate) of the first unmanned aerial vehicle, a takeoffdate of the first unmanned aerial vehicle, or a takeoff time of thefirst unmanned aerial vehicle.

Specifically, descriptions are provided with reference to FIG. 4. Theflight tags obtained after the first unmanned aerial vehicle flies for aplurality of times can be displayed in the client running on the controlterminal. For example, takeoff geographic locations included in a firstflight tag (represented by using “occupying for a first time”) are asfollows: “Eiffel Tower, France (Sep. 24, 2015)”, “Madrid, Spain (Jul.17, 2015)”, “Hokkaido, Japan (Jun. 4, 2015)”, and “Paradise Island, theMaldives (Apr. 30, 2015)”; and takeoff geographic locations included ina second flight tag (represented by “flying across”) are as follows:“Triumphal arch, France (Sep. 23, 2015)”, “Barcelona, Spain (Jul. 19,2015)”, and “Tokyo, Japan (Jun. 6, 2015)”.

According to the embodiment provided in this application, the obtainedflight tag is displayed in the client running on the control terminal,so that different users can share the flight tag in social space, andshare different flying experiences by using the flight tag, therebysatisfying different actual requirements of the different users.

In an optional solution, after the sending the takeoff geographiclocation of the first unmanned aerial vehicle to a server, and beforethe obtaining a flight tag returned by the server, the method furtherincludes:

S1: The server receives the takeoff geographic location.

S2: The server determines whether there is a takeoff geographic locationin stored takeoff geographic locations that is the same as the takeoffgeographic location of the first unmanned aerial vehicle.

S3: If yes, the server sends a first flight tag, the first flight tagbeing used for indicating that the first unmanned aerial vehicle is notan unmanned aerial vehicle first taking off from the takeoff geographiclocation of the first unmanned aerial vehicle, and the flight tagincluding the first flight tag.

S3: If no, the server sends a second flight tag, the second flight tagbeing used for indicating that the first unmanned aerial vehicle is anunmanned aerial vehicle first taking off from the takeoff geographiclocation of the first unmanned aerial vehicle, and the flight tagincluding the second flight tag.

Optionally, in this embodiment, the foregoing server compares storedtakeoff geographic locations with the takeoff geographic location of thefirst unmanned aerial vehicle, to determine whether there is a takeoffgeographic location in a database established in the server that is thesame as the takeoff geographic location of the first unmanned aerialvehicle, to send different flight tags according to a determiningresult. Therefore, it is ensured that the client running on the controlterminal obtains an accurate flight tag.

Optionally, in this embodiment, the determining whether there is atakeoff geographic location in stored takeoff geographic locations thatis the same as the takeoff geographic location of the first unmannedaerial vehicle includes at least one of the following:

1) determining whether location information of the takeoff geographiclocation of the first unmanned aerial vehicle is consistent withlocation information of the stored takeoff geographic locations; or

2) determining whether region indication information in locationinformation of the takeoff geographic location of the first unmannedaerial vehicle is consistent with region indication information inlocation information of the stored takeoff geographic locations, theregion indication information being a part of the location information.

That is, a principle for determining a same takeoff geographic locationmay include but is not limited to at least one of the following: thelocation information is completely consistent, or the region indicationinformation (a part of the location information) used for indicating aregion in which the first unmanned aerial vehicle is located isconsistent.

Optionally, in this embodiment, that the first flight tag is sent to aclient includes: obtaining a geographic name corresponding to thetakeoff geographic location of the first unmanned aerial vehicle, andsending the first flight tag at least including the geographic name;that the second flight tag is sent to a client includes: obtaining ageographic name corresponding to the takeoff geographic location of thefirst unmanned aerial vehicle, storing a correspondence between thetakeoff geographic location of the first unmanned aerial vehicle and theobtained geographic name, and sending the second flight tag at leastincluding the geographic name.

Optionally, in this embodiment, the foregoing server may, but is notlimited to, adjust (e.g., update), according to the obtained takeoffgeographic location of the unmanned aerial vehicle, the takeoffgeographic locations stored in the database of the server. For example,the obtained takeoff geographic location of the unmanned aerial vehiclecan be included in the takeoff geographic locations stored in thedatabase of the server. Specifically, when the second flight tag usedfor indicating that the first unmanned aerial vehicle is an unmannedaerial vehicle first taking off from the takeoff geographic location ofthe first unmanned aerial vehicle is obtained, the geographic namecorresponding to the takeoff geographic location of the first unmannedaerial vehicle is obtained, and the correspondence between the takeoffgeographic location of the first unmanned aerial vehicle and theobtained geographic name is stored, to newly add a takeoff geographiclocation to the database.

According to the embodiment provided in this application, the takeoffgeographic location obtained when the unmanned aerial vehicle takes offis sent to the server, so that the server establishes a common databaseof unmanned aerial vehicles on the server by using the obtained takeoffgeographic location of the unmanned aerial vehicle. Further, thedatabase is used for establishing interaction between the client runningon the control terminal and the server, to implement sharing of thetakeoff geographic location of the unmanned aerial vehicle, and returnthe flight tag corresponding to the unmanned aerial vehicle to thecontrol terminal according to the takeoff geographic location of theunmanned aerial vehicle. Therefore, the foregoing flight tag of theunmanned aerial vehicle can be shared in social space of the client.

It should be noted that, to simplify the description, the foregoingmethod embodiments are described as a series of action combination. Butpersons skilled in the art should know that this application is notlimited to any described order of the action, as some steps can adoptother orders or can be performed simultaneously according to thisapplication. Secondarily, persons skilled in the art should know thatthe embodiments described in the specification belong to exemplaryembodiments and not all the involved actions and modules are necessaryfor this application.

Through the descriptions of the preceding embodiments, persons skilledin the art may understand that the methods according to the foregoingembodiments may be implemented by software and a universal hardwareplatform, and certainly may also be implemented by hardware. Based onsuch an understanding, the technical solutions of this application orthe part that makes contributions to the existing technology may besubstantially embodied in the form of a software product. The computersoftware product is stored in a storage medium (for example, a ROM/RAM,a magnetic disk, or an optical disc), and contains instructions forinstructing a terminal device (which may be a mobile phone, a computer,a server, or a network device) to perform functions of the embodimentsof this application.

Embodiment 2

According to this embodiment of this application, a flight tag obtainingmethod is further provided. As shown in FIG. 7, the method includes:

S702: Receive a takeoff geographic location of a first unmanned aerialvehicle when the first unmanned aerial vehicle takes off sent by aclient, the client running on a control terminal and being configured tocontrol the takeoff of the first unmanned aerial vehicle.

S704: Determine whether there is a takeoff geographic location in storedtakeoff geographic locations that is the same as the takeoff geographiclocation of the first unmanned aerial vehicle.

S706: If yes, send a first flight tag to the client, the first flighttag being used for indicating that the first unmanned aerial vehicle isnot an unmanned aerial vehicle first taking off from the takeoffgeographic location of the first unmanned aerial vehicle.

S708: If no, send a second flight tag to the client, the second flighttag being used for indicating that the first unmanned aerial vehicle isan unmanned aerial vehicle first taking off from the takeoff geographiclocation of the first unmanned aerial vehicle.

Optionally, in this embodiment, the foregoing flight tag obtainingmethod may be applied to, but not limited to, a process in which aclient running on a control terminal obtains a flight tag of an unmannedaerial vehicle. The foregoing client running on the control terminal isconfigured to control takeoff of the unmanned aerial vehicle. Forexample, after receiving the takeoff geographic location of the firstunmanned aerial vehicle when the first unmanned aerial vehicle takes offsent by the client, a server determines whether there is a takeoffgeographic location in stored takeoff geographic locations that is thesame as the takeoff geographic location of the first unmanned aerialvehicle, to send different first flight tags or second flight tags tothe client according to different determining results, the clientrunning on the control terminal and being configured to control thetakeoff of the first unmanned aerial vehicle. As shown in FIG. 3, theflight tag of the unmanned aerial vehicle returned by the server isdisplayed in the client (a user name is ID_01) running on the controlterminal. For example, the flight tags returned by the server include aflight tag_1 and a flight tag_2. For example, the flight tags may be“occupying for a first time” or “flying across”. The foregoing is merelyexemplary, and no limitation is set in this embodiment.

It should be noted that, in this embodiment, the server receives atakeoff geographic location of a first unmanned aerial vehicle when thefirst unmanned aerial vehicle takes off sent by a client, the clientrunning on a control terminal and being configured to control thetakeoff of the first unmanned aerial vehicle; determines whether thereis a takeoff geographic location in stored takeoff geographic locationsthat is the same as the takeoff geographic location of the firstunmanned aerial vehicle; and if yes, sends a first flight tag to theclient, the first flight tag being used for indicating that the firstunmanned aerial vehicle is not an unmanned aerial vehicle first takingoff from the takeoff geographic location of the first unmanned aerialvehicle; or if no, sends a second flight tag to the client, the secondflight tag being used for indicating that the first unmanned aerialvehicle is an unmanned aerial vehicle first taking off from the takeoffgeographic location of the first unmanned aerial vehicle, and the flighttag being used for indicating whether the first unmanned aerial vehicleis an unmanned aerial vehicle first taking off from the takeoffgeographic location of the first unmanned aerial vehicle. The serverobtains a corresponding flight tag according to the obtained takeoffgeographic location, and sends the flight tag to the client, so that theserver establishes a common database of unmanned aerial vehicles on theserver by using the obtained takeoff geographic location of the unmannedaerial vehicle. Further, interaction is established between the clientrunning on the control terminal and the server by using the database, toimplement sharing of the takeoff geographic location of the unmannedaerial vehicle, and return the flight tag corresponding to the unmannedaerial vehicle to the control terminal according to the takeoffgeographic location of the unmanned aerial vehicle. Therefore, theforegoing flight tag of the unmanned aerial vehicle can be shared insocial space of the client.

Optionally, in this embodiment, the flight tag may include but is notlimited to at least one of the following: a first flight tag used forindicating that the first unmanned aerial vehicle is not an unmannedaerial vehicle first taking off from the takeoff geographic location ofthe first unmanned aerial vehicle, or a second flight tag used forindicating that the first unmanned aerial vehicle is an unmanned aerialvehicle first taking off from the takeoff geographic location of thefirst unmanned aerial vehicle.

Optionally, in this embodiment, the foregoing flight tag may further bebut is not limited to being used for indicating at least one of thefollowing: a geographic name corresponding to the takeoff geographiclocation of the first unmanned aerial vehicle, a takeoff date of thefirst unmanned aerial vehicle, or a takeoff time of the first unmannedaerial vehicle. For example, a first unmanned aerial vehicle iscontrolled by a client (a user name is ID_01) running on a controlterminal. After the first unmanned aerial vehicle flies for a pluralityof times, an obtained flight tag displayed in the client may be shown inFIG. 4. Takeoff geographic locations included in a first flight tag(represented by using “occupying for a first time”) are as follows:“Eiffel Tower, France (Sep. 24, 2015)”, “Madrid, Spain (Jul. 17, 2015)”,“Hokkaido, Japan (Jun. 4, 2015)”, and “Paradise Island, the Maldives(Apr. 30, 2015)”. Takeoff geographic locations included in a secondflight tag (represented by using “flying across”) are as follows:“Triumphal arch, France (Sep. 23, 2015)”, “Barcelona, Spain (Jul. 19,2015)”, and “Tokyo, Japan (Jun. 6, 2015)”.

Optionally, in this embodiment, the takeoff geographic location of theforegoing first unmanned aerial vehicle may include but is not limitedto one of the following: 1) a geographic location of the first unmannedaerial vehicle when the first unmanned aerial vehicle takes off; or 2) ageographic location of the control terminal when the first unmannedaerial vehicle takes off. When the takeoff geographic location of thefirst unmanned aerial vehicle is the geographic location of the firstunmanned aerial vehicle when the first unmanned aerial vehicle takesoff, the takeoff geographic location may be obtained in, but is notlimited to, at least one of the following manners: 1) The controlterminal obtains the geographic location of the first unmanned aerialvehicle collected by the first unmanned aerial vehicle when the firstunmanned aerial vehicle takes off; or 2) The control terminal obtains,by detection, the geographic location of the first unmanned aerialvehicle when the first unmanned aerial vehicle takes off.

Optionally, in this embodiment, the determining whether there is atakeoff geographic location in stored takeoff geographic locations thatis the same as the takeoff geographic location of the first unmannedaerial vehicle includes at least one of the following:

1) determining whether location information of the takeoff geographiclocation of the first unmanned aerial vehicle is consistent withlocation information of the stored takeoff geographic locations; or

2) determining whether region indication information in locationinformation of the takeoff geographic location of the first unmannedaerial vehicle is consistent with region indication information inlocation information of the stored takeoff geographic locations, theregion indication information being a part of the location information.

That is, a principle for determining a same takeoff geographic locationmay include but is not limited to at least one of the following: thelocation information is completely consistent, or the region indicationinformation (a part of the location information) used for indicating aregion in which the first unmanned aerial vehicle is located isconsistent.

Optionally, in this embodiment, that the first flight tag is sent to aclient includes: obtaining a geographic name corresponding to thetakeoff geographic location of the first unmanned aerial vehicle, andsending the first flight tag at least including the geographic name;that the second flight tag is sent to a client includes: obtaining ageographic name corresponding to the takeoff geographic location of thefirst unmanned aerial vehicle, storing a correspondence between thetakeoff geographic location of the first unmanned aerial vehicle and theobtained geographic name, and sending the second flight tag at leastincluding the geographic name.

Optionally, in this embodiment, the foregoing server may adjust, but isnot limited to, adjusting, according to the obtained takeoff geographiclocation of the unmanned aerial vehicle, the takeoff geographiclocations stored in the database of the server. Specifically, when thesecond flight tag used for indicating that the first unmanned aerialvehicle is an unmanned aerial vehicle first taking off from the takeoffgeographic location of the first unmanned aerial vehicle is obtained,the geographic name corresponding to the takeoff geographic location ofthe first unmanned aerial vehicle is obtained, and the correspondencebetween the takeoff geographic location of the first unmanned aerialvehicle and the obtained geographic name is stored, to newly add atakeoff geographic location to the database.

According to the embodiment provided in this embodiment, the serverobtains a corresponding flight tag according to the obtained takeoffgeographic location, and sends the flight tag to the client, so that theserver establishes a common database of unmanned aerial vehicles on theserver by using the obtained takeoff geographic location of the unmannedaerial vehicle. Further, interaction is established between the clientrunning on the control terminal and the server by using the database, toimplement sharing of the takeoff geographic location of the unmannedaerial vehicle, and return the flight tag corresponding to the unmannedaerial vehicle to the control terminal according to the takeoffgeographic location of the unmanned aerial vehicle. Therefore, theforegoing flight tag of the unmanned aerial vehicle can be shared insocial space of the client.

In an optional solution, the determining whether there is a takeoffgeographic location in stored takeoff geographic locations that is thesame as the takeoff geographic location of the first unmanned aerialvehicle includes at least one of the following:

1) determining whether location information of the takeoff geographiclocation of the first unmanned aerial vehicle is consistent withlocation information of the stored takeoff geographic locations; or

2) determining whether region indication information in locationinformation of the takeoff geographic location of the first unmannedaerial vehicle is consistent with region indication information inlocation information of the stored takeoff geographic locations, theregion indication information being a part of the location information.

That is, a principle for determining a same takeoff geographic locationmay include but is not limited to at least one of the following: thelocation information is completely consistent, or the region indicationinformation (a part of the location information) used for indicating aregion in which the first unmanned aerial vehicle is located isconsistent.

In an optional solution,

1) the sending a first flight tag to the client includes: obtaining ageographic name corresponding to the takeoff geographic location of thefirst unmanned aerial vehicle, and sending the first flight tag at leastincluding the geographic name; and

2) the sending a second flight tag to the client includes: obtaining ageographic name corresponding to the takeoff geographic location of thefirst unmanned aerial vehicle, storing a correspondence between thetakeoff geographic location of the first unmanned aerial vehicle and theobtained geographic name, and sending the second flight tag at leastincluding the geographic name.

Optionally, in this embodiment, the foregoing server may adjust, but isnot limited to, adjusting, according to the obtained takeoff geographiclocation of the unmanned aerial vehicle, the takeoff geographiclocations stored in the database of the server. Specifically, when thesecond flight tag used for indicating that the first unmanned aerialvehicle is an unmanned aerial vehicle first taking off from the takeoffgeographic location of the first unmanned aerial vehicle is obtained,the geographic name corresponding to the takeoff geographic location ofthe first unmanned aerial vehicle is obtained, and the correspondencebetween the takeoff geographic location of the first unmanned aerialvehicle and the obtained geographic name is stored, to newly add atakeoff geographic location to the database.

It should be noted that, to simplify the description, the foregoingmethod embodiments are described as a series of action combination. Butpersons skilled in the art should know that this application is notlimited to any described sequence of the action, as some steps can adoptother sequences or can be performed simultaneously according to thisapplication. Secondarily, persons skilled in the art should know thatthe embodiments described in the specification belong to exemplaryembodiments and the involved actions and not all modules are necessaryfor this application.

Through the descriptions of the preceding embodiments, persons skilledin the art may understand that the methods according to the foregoingembodiments may be implemented by software and a universal hardwareplatform, and certainly may also be implemented by hardware. Based onsuch an understanding, the technical solutions of this application orthe part that makes contributions to the existing technology may besubstantially embodied in the form of a software product. The computersoftware product is stored in a storage medium (for example, a ROM/RAM,a magnetic disk, or an optical disc), and contains several instructionsfor instructing a terminal device (which may be a mobile phone, acomputer, a server, or a network device) to execute the apparatusaccording to the embodiments of this application.

Embodiment 3

According to this embodiment of this application, a flight tag obtainingterminal is provided. As shown in FIG. 8, the terminal includes:

1) a first obtaining unit 802, configured to obtain a takeoff geographiclocation of a first unmanned aerial vehicle when the first unmannedaerial vehicle takes off;

2) a first sending unit 804, configured to send the takeoff geographiclocation of the first unmanned aerial vehicle to a server; and

3) a second obtaining unit 806, configured to obtain a flight tagreturned by the server, the flight tag being used for indicating whetherthe first unmanned aerial vehicle is an unmanned aerial vehicle firsttaking off from the takeoff geographic location of the first unmannedaerial vehicle.

Optionally, in this embodiment, the foregoing flight tag obtainingterminal may be but is not limited to being applied to a process inwhich a client running on a control terminal obtains a flight tag of anunmanned aerial vehicle. The foregoing client running on the controlterminal is configured to control takeoff of the unmanned aerialvehicle. For example, after an obtained takeoff geographic location of afirst unmanned aerial vehicle when the first unmanned aerial vehicletakes off is sent to a server, a flight tag of the first unmanned aerialvehicle returned by the server is obtained. In addition, as shown inFIG. 3, the flight tag of the unmanned aerial vehicle returned by theserver is displayed in the client (a user name is ID_01) running on thecontrol terminal. For example, the flight tags returned by the serverinclude a flight tag_1 and a flight tag_2. For example, the flight tagsmay be “occupying for a first time” or “flying across”. The foregoing ismerely exemplary, and no limitation is set in this embodiment.

It should be noted that, in this embodiment, a client running on acontrol terminal obtains a takeoff geographic location of a firstunmanned aerial vehicle when the first unmanned aerial vehicle takesoff; sends the takeoff geographic location to a server; and obtains aflight tag returned by the server, the flight tag being used forindicating whether the first unmanned aerial vehicle is an unmannedaerial vehicle first taking off from the takeoff geographic location ofthe first unmanned aerial vehicle. The takeoff geographic locationobtained when the unmanned aerial vehicle takes off is sent to theserver, so that the server establishes a common database of unmannedaerial vehicles on the server by using the obtained takeoff geographiclocation of the unmanned aerial vehicle. Further, the database is usedfor establishing interaction between the client running on the controlterminal and the server, to implement sharing of the takeoff geographiclocation of the unmanned aerial vehicle, and return the flight tagcorresponding to the unmanned aerial vehicle to the control terminalaccording to the takeoff geographic location of the unmanned aerialvehicle. Therefore, the foregoing flight tag of the unmanned aerialvehicle can be shared in social space of the client.

Optionally, in this embodiment, after the sending the takeoff geographiclocation of the first unmanned aerial vehicle to a server, and beforethe obtaining a flight tag returned by the server, the method furtherincludes: determining, by the server, whether there is a takeoffgeographic location in stored takeoff geographic locations that is thesame as the received takeoff geographic location of the first unmannedaerial vehicle; and sending a corresponding flight tag according to adetermining result. The flight tag may include but is not limited to atleast one of the following: a first flight tag used for indicating thatthe first unmanned aerial vehicle is not an unmanned aerial vehiclefirst taking off from the takeoff geographic location of the firstunmanned aerial vehicle, or a second flight tag used for indicating thatthe first unmanned aerial vehicle is an unmanned aerial vehicle firsttaking off from the takeoff geographic location of the first unmannedaerial vehicle.

Optionally, in this embodiment, the foregoing flight tag may further bebut is not limited to being used for indicating at least one of thefollowing: a geographic name corresponding to the takeoff geographiclocation of the first unmanned aerial vehicle, a takeoff date of thefirst unmanned aerial vehicle, or a takeoff time of the first unmannedaerial vehicle. For example, a first unmanned aerial vehicle iscontrolled by a client (a user name is ID_01) running on a controlterminal. After the first unmanned aerial vehicle flies for a pluralityof times, an obtained flight tag displayed in the client may be shown inFIG. 4. Takeoff geographic locations included in a first flight tag(represented by using “occupying for a first time”) are as follows:“Eiffel Tower, France (Sep. 24, 2015)”, “Madrid, Spain (Jul. 17, 2015)”,“Hokkaido, Japan (Jun. 4, 2015)”, and “Paradise Island, the Maldives(Apr. 30, 2015)”. Takeoff geographic locations included in a secondflight tag (represented by using “flying across”) are as follows:“Triumphal arch, France (Sep. 23, 2015)”, “Barcelona, Spain (Jul. 19,2015)”, and “Tokyo, Japan (Jun. 6, 2015)”.

Optionally, in this embodiment, the takeoff geographic location of theforegoing first unmanned aerial vehicle may include but is not limitedto one of the following: 1) a geographic location of the first unmannedaerial vehicle when the first unmanned aerial vehicle takes off; or 2) ageographic location of the control terminal when the first unmannedaerial vehicle takes off. When the takeoff geographic location of thefirst unmanned aerial vehicle is the geographic location of the firstunmanned aerial vehicle when the first unmanned aerial vehicle takesoff, the takeoff geographic location may be obtained in, but is notlimited to, at least one of the following manners: 1) The controlterminal obtains the geographic location of the first unmanned aerialvehicle collected by the first unmanned aerial vehicle when the firstunmanned aerial vehicle takes off; or 2) The control terminal obtains,by detection, the geographic location of the first unmanned aerialvehicle when the first unmanned aerial vehicle takes off.

Optionally, in this embodiment, the sending the takeoff geographiclocation of the first unmanned aerial vehicle to a server includes oneof the following:

1) when the first unmanned aerial vehicle takes off, sending the takeoffgeographic location of the first unmanned aerial vehicle to the server;or

2) after the first unmanned aerial vehicle takes off, sending thetakeoff geographic location of the first unmanned aerial vehicle to theserver.

It should be noted that, in manner 1) of this embodiment, the takeoffgeographic location of the first unmanned aerial vehicle is sent to theserver in real time when the first unmanned aerial vehicle takes off, sothat the server can implement real-time comparison and real-timefeedback, to ensure that the client running on the control terminal canobtain in time the flight tag matched the first unmanned aerial vehicle,and the social space of the client can update and display the obtainedflight tag in real time. Further, data recorded in the database of theserver can further be updated in real time, to ensure the accuracy andupdate efficiency of the database, so that a plurality of users caninvoke the data in the database at the same time, to implement thefeasibility of multi-user interaction.

In addition, in manner 2) of this embodiment, the takeoff geographiclocation of the first unmanned aerial vehicle may alternatively be sentto the server after the first unmanned aerial vehicle takes off, so thatthe server is synchronized with the obtained takeoff geographic locationof the first unmanned aerial vehicle after a time interval. Asynchronization process in which the takeoff geographic location of thefirst unmanned aerial vehicle is sent to the server is separated, thatis, a plurality of takeoff geographic locations obtained at particulartime intervals is sent to the server together, to reduce a number ofsending operations, and therefore improve the efficiency of sending thetakeoff geographic location to the server.

Optionally, in this embodiment, the after the first unmanned aerialvehicle takes off, sending the takeoff geographic location of the firstunmanned aerial vehicle to the server in manner 2) includes one of thefollowing:

(1) after the first unmanned aerial vehicle takes off, obtaining asending instruction, and sending, in response to the sendinginstruction, the takeoff geographic location of the first unmannedaerial vehicle to the server; or

(2) after the first unmanned aerial vehicle takes off, determiningwhether a preset sending moment is reached, and when it is determinedthat the sending moment is reached, sending the takeoff geographiclocation of the first unmanned aerial vehicle to the server.

That is, after the first unmanned aerial vehicle takes off, the takeoffgeographic location of the first unmanned aerial vehicle may be sent tothe server in response to the obtained sending instruction, or theobtained takeoff geographic location of the first unmanned aerialvehicle may be sent to the server at the preset sending moment.

It should be noted that, in this embodiment, the foregoing sendinginstruction may be but is not limited to a sending instruction triggeredby a user by means of an input operation. The input operation mayinclude but is not limited to at least one of the following: clicking apredetermined trigger button, collecting predetermined voice, orobtaining a predetermined motion sensing gesture.

In addition, in this embodiment, the foregoing preset sending moment mayinclude but is not limited to at least one of the following: a momentsatisfying a predetermined condition, or a preset cycle end moment. Forexample, the predetermined condition may be detecting a preconfigurednetwork signal, such as a 4G network signal or a WiFi signal.

Specifically, descriptions are provided with reference to the followingexamples. As shown in FIG. 5, in the example, that a geographic locationof a first unmanned aerial vehicle when the first unmanned aerialvehicle takes off is a takeoff geographic location of the first unmannedaerial vehicle is used as an example.

S502: A client 504 running on a control terminal obtains a geographiclocation of a first unmanned aerial vehicle collected by the firstunmanned aerial vehicle 502 when the first unmanned aerial vehicle takesoff.

S504: The client 504 running on the control terminal sends the takeoffgeographic location of the first unmanned aerial vehicle to the server506.

S506: The server 506 determines whether there is a takeoff geographiclocation in stored takeoff geographic locations that is the same as thereceived takeoff geographic location of the first unmanned aerialvehicle; and obtains a corresponding flight tag according to adetermining result.

S508: The server 506 returns the flight tag to the client 504 running onthe control terminal.

S510: The client 504 running on the control terminal displays the flighttag.

According to the embodiment provided in this application, the takeoffgeographic location obtained when the unmanned aerial vehicle takes offis sent to the server, so that the server establishes a common databaseof unmanned aerial vehicles on the server by using the obtained takeoffgeographic location of the unmanned aerial vehicle. Further, thedatabase is used for establishing interaction between the client runningon the control terminal and the server, to implement sharing of thetakeoff geographic location of the unmanned aerial vehicle, and returnthe flight tag corresponding to the unmanned aerial vehicle to thecontrol terminal according to the takeoff geographic location of theunmanned aerial vehicle. Therefore, the foregoing flight tag of theunmanned aerial vehicle can be shared in social space of the client, toresolve a technical problem that a flight tag of an unmanned aerialvehicle cannot be obtained by using the existing technology.

In an optional solution, the first sending unit 804 includes one of thefollowing:

1) a first sending module, configured to: when the first unmanned aerialvehicle takes off, send the takeoff geographic location of the firstunmanned aerial vehicle to the server; or

2) a second sending module, configured to: after the first unmannedaerial vehicle takes off, send the takeoff geographic location of thefirst unmanned aerial vehicle to the server.

It should be noted that, in this embodiment, the takeoff geographiclocation of the first unmanned aerial vehicle may be sent to the serverwhen the first unmanned aerial vehicle takes off or after the firstunmanned aerial vehicle takes off. That is, the takeoff geographiclocation may be sent to the server in real time, so that the server canimplement real-time comparison and real-time feedback, to ensure thatthe client running on the control terminal can obtain in time the flighttag matched the first unmanned aerial vehicle, and the social space ofthe client can update and display the obtained flight tag in real time.Alternatively, the synchronization process may be separated, to firststore a plurality of takeoff geographic locations obtained at particulartime intervals, and then send the obtained takeoff geographic locationsto the server together, to reduce a number of sending operations, andimprove the efficiency of sending the takeoff geographic location to theserver.

Optionally, in this embodiment, in manner 2), the foregoing takeoffgeographic location of the first unmanned aerial vehicle may be firststored in the control terminal, or may be stored in another third-partystorage medium. No limitation is set thereto in this embodiment.

According to the embodiment provided in this application, the takeoffgeographic location of the first unmanned aerial vehicle is sent whenthe first unmanned aerial vehicle takes off or after the first unmannedaerial vehicle takes off, to select different sending moments accordingto different application scenarios, to ensure that the flight tagcorresponding to the takeoff geographic location can be accuratelyobtained in time.

In an optional solution, the second sending module includes one of thefollowing:

(1) a first sending submodule, configured to: after the first unmannedaerial vehicle takes off, obtain a sending instruction, and send, inresponse to the sending instruction, the takeoff geographic location ofthe first unmanned aerial vehicle to the server; or

2) a second sending submodule, configured to: after the first unmannedaerial vehicle takes off, determine whether a preset sending moment isreached, and when it is determined that the sending moment is reached,send the takeoff geographic location of the first unmanned aerialvehicle to the server.

Optionally, in this embodiment, after the first unmanned aerial vehicletakes off, the takeoff geographic location of the first unmanned aerialvehicle may be sent to the server in response to the obtained sendinginstruction. The foregoing sending instruction may be but is not limitedto a sending instruction triggered by a user by means of an inputoperation. The input operation may include but is not limited to atleast one of the following: clicking a predetermined trigger button,collecting predetermined voice, or obtaining a predetermined motionsensing gesture. For example, a control interface in which the clientrunning on the control terminal controls the first unmanned aerialvehicle is shown in FIG. 6. The client can control the first unmannedaerial vehicle to perform different operations of “returning andlanding”, “emergent suspension”, and “following mode”, or control thefirst unmanned aerial vehicle to move according to directions indicatedby arrows. In addition, the sending instruction of sending the takeoffgeographic location of the first unmanned aerial vehicle to the servermay alternatively be triggered by using a “control button” after thefirst unmanned aerial vehicle takes off (or when the first unmannedaerial vehicle takes off).

Optionally, in this embodiment, after the first unmanned aerial vehicletakes off, the obtained takeoff geographic location of the firstunmanned aerial vehicle may alternatively be sent to the server at apreset sending moment. The foregoing preset sending moment may includebut is not limited to at least one of the following: a moment satisfyinga predetermined condition, or a preset cycle end moment. For example,the predetermined condition may be detecting a preconfigured networksignal, such as a 4G network signal or a WiFi signal.

According to the embodiment provided in this application, the controlterminal is triggered in different manners to send the takeoffgeographic location of the first unmanned aerial vehicle to the server,to implement operation diversification and facilitate operationsperformed by a user, thereby improving the user experience.

In an optional solution, the first obtaining unit 802 includes one ofthe following:

1) a third obtaining module, configured to obtain a geographic locationof the first unmanned aerial vehicle when the first unmanned aerialvehicle takes off, the geographic location of the first unmanned aerialvehicle being used as the takeoff geographic location of the firstunmanned aerial vehicle; or

2) a fourth obtaining module, configured to: obtain a geographiclocation of a control terminal when the first unmanned aerial vehicletakes off, a client running on the control terminal controlling thetakeoff of the first unmanned aerial vehicle; and use the geographiclocation of the control terminal as the takeoff geographic location ofthe first unmanned aerial vehicle.

Optionally, in this embodiment, the geographic location of the firstunmanned aerial vehicle when the first unmanned aerial vehicle takes offmay be obtained in, but is not limited to, at least one of the followingmanners: 1) The control terminal obtains the geographic location of thefirst unmanned aerial vehicle collected by the first unmanned aerialvehicle when the first unmanned aerial vehicle takes off; or 2) Thecontrol terminal obtains, by detection, the geographic location of thefirst unmanned aerial vehicle when the first unmanned aerial vehicletakes off.

According to the embodiment provided in this application, the clientrunning on the control terminal can obtain the takeoff geographiclocation of the first unmanned aerial vehicle collected by the firstunmanned aerial vehicle when the first unmanned aerial vehicle takesoff, or can obtain, by self-detection, the takeoff geographic locationof the first unmanned aerial vehicle when the first unmanned aerialvehicle takes off. The takeoff geographic location of the first unmannedaerial vehicle is obtained in different manners, to satisfy actualrequirements of different users, and ensure the accuracy of the obtainedflight tag.

In an optional solution, the terminal further includes:

1) a display unit, configured to: after the flight tag returned by theserver is obtained, display the flight tag in a client running on acontrol terminal, the client controlling the takeoff of the firstunmanned aerial vehicle, and the flight tag further being used forindicating at least one of the following: a geographic namecorresponding to the takeoff geographic location of the first unmannedaerial vehicle, a takeoff date of the first unmanned aerial vehicle, ora takeoff time of the first unmanned aerial vehicle.

Optionally, in this embodiment, the foregoing flight tag may include butis not limited to at least one of the following: a first flight tag usedfor indicating that the first unmanned aerial vehicle is not an unmannedaerial vehicle first taking off from the takeoff geographic location ofthe first unmanned aerial vehicle, or a second flight tag used forindicating that the first unmanned aerial vehicle is an unmanned aerialvehicle first taking off from the takeoff geographic location of thefirst unmanned aerial vehicle. In addition, the foregoing flight tag mayfurther be used for indicating at least one of the following: ageographic name (for example, a location name) corresponding to thetakeoff geographic location (for example, a location coordinate) of thefirst unmanned aerial vehicle, a takeoff date of the first unmannedaerial vehicle, or a takeoff time of the first unmanned aerial vehicle.

Specifically, descriptions are provided with reference to FIG. 4. Theflight tag obtained after the first unmanned aerial vehicle flies for aplurality of times can be displayed in the client running on the controlterminal. For example, takeoff geographic locations included in a firstflight tag (represented by using “occupying for a first time”) are asfollows: “Eiffel Tower, France (Sep. 24, 2015)”, “Madrid, Spain (Jul.17, 2015)”, “Hokkaido, Japan (Jun. 4, 2015)”, and “Paradise Island, theMaldives (Apr. 30, 2015)”; and takeoff geographic locations included ina second flight tag (represented by “flying across”) are as follows:“Triumphal arch, France (Sep. 23, 2015)”, “Barcelona, Spain (Jul. 19,2015)”, and “Tokyo, Japan (Jun. 6, 2015)”.

According to the embodiment provided in this application, the obtainedflight tag is displayed in the client running on the control terminal,so that different users can share the flight tag in social space, andshare different flying experiences by using the flight tag, therebysatisfying different actual requirements of the different users.

Embodiment 4

According to this embodiment of this application, a flight tag obtainingserver is provided. As shown in FIG. 9, the server includes:

1) a receiving unit 902, configured to receive a takeoff geographiclocation of a first unmanned aerial vehicle when the first unmannedaerial vehicle takes off sent by a client, the client running on acontrol terminal and being configured to control the takeoff of thefirst unmanned aerial vehicle;

2) a determining unit 904, configured to determine whether there is atakeoff geographic location in stored takeoff geographic locations thatis the same as the takeoff geographic location of the first unmannedaerial vehicle;

3) a first sending unit 906, configured to: when there is a takeoffgeographic location that is the same as the takeoff geographic locationof the first unmanned aerial vehicle, send a first flight tag to theclient, the first flight tag being used for indicating that the firstunmanned aerial vehicle is not an unmanned aerial vehicle first takingoff from the takeoff geographic location of the first unmanned aerialvehicle; and

4) a second sending unit 908, configured to: when there is no takeoffgeographic location that is the same as the takeoff geographic locationof the first unmanned aerial vehicle, send a second flight tag to theclient, the second flight tag being used for indicating that the firstunmanned aerial vehicle is an unmanned aerial vehicle first taking offfrom the takeoff geographic location of the first unmanned aerialvehicle.

Optionally, in this embodiment, the foregoing flight tag obtainingserver may be but is not limited to being applied to a process in whicha client running on a control terminal obtains a flight tag of anunmanned aerial vehicle. The foregoing client running on the controlterminal is configured to control takeoff of the unmanned aerialvehicle. For example, after receiving the takeoff geographic location ofthe first unmanned aerial vehicle when the first unmanned aerial vehicletakes off sent by the client, a server determines whether there is atakeoff geographic location in stored takeoff geographic locations thatis the same as the takeoff geographic location of the first unmannedaerial vehicle, to send different first flight tags or second flighttags to the client according to different determining results, theclient running on the control terminal and being configured to controlthe takeoff of the first unmanned aerial vehicle. As shown in FIG. 3,the flight tag of the unmanned aerial vehicle returned by the server isdisplayed in the client (a user name is ID_01) running on the controlterminal. For example, the flight tags returned by the server include aflight tag_1 and a flight tag_2. For example, the flight tags may be“occupying for a first time” or “flying across”. The foregoing is merelyexemplary, and no limitation is set in this embodiment.

It should be noted that, in this embodiment, the server receives atakeoff geographic location of a first unmanned aerial vehicle when thefirst unmanned aerial vehicle takes off sent by a client, the clientrunning on a control terminal and being configured to control thetakeoff of the first unmanned aerial vehicle; determines whether thereis a takeoff geographic location in stored takeoff geographic locationsthat is the same as the takeoff geographic location of the firstunmanned aerial vehicle; and if yes, sends a first flight tag to theclient, the first flight tag being used for indicating that the firstunmanned aerial vehicle is not an unmanned aerial vehicle first takingoff from the takeoff geographic location of the first unmanned aerialvehicle; or if no, sends a second flight tag to the client, the secondflight tag being used for indicating that the first unmanned aerialvehicle is an unmanned aerial vehicle first taking off from the takeoffgeographic location of the first unmanned aerial vehicle, and the flighttag being used for indicating whether the first unmanned aerial vehicleis an unmanned aerial vehicle first taking off from the takeoffgeographic location of the first unmanned aerial vehicle. The serverobtains a corresponding flight tag according to the obtained takeoffgeographic location, and sends the flight tag to the client, so that theserver establishes a common database of unmanned aerial vehicles on theserver by using the obtained takeoff geographic location of the unmannedaerial vehicle. Further, interaction is established between the clientrunning on the control terminal and the server by using the database, toimplement sharing of the takeoff geographic location of the unmannedaerial vehicle, and return the flight tag corresponding to the unmannedaerial vehicle to the control terminal according to the takeoffgeographic location of the unmanned aerial vehicle. Therefore, theforegoing flight tag of the unmanned aerial vehicle can be shared insocial space of the client.

Optionally, in this embodiment, the flight tag may include but is notlimited to at least one of the following: a first flight tag used forindicating that the first unmanned aerial vehicle is not an unmannedaerial vehicle first taking off from the takeoff geographic location ofthe first unmanned aerial vehicle, or a second flight tag used forindicating that the first unmanned aerial vehicle is an unmanned aerialvehicle first taking off from the takeoff geographic location of thefirst unmanned aerial vehicle.

Optionally, in this embodiment, the foregoing flight tag may further bebut is not limited to being used for indicating at least one of thefollowing: a geographic name corresponding to the takeoff geographiclocation of the first unmanned aerial vehicle, a takeoff date of thefirst unmanned aerial vehicle, or a takeoff time of the first unmannedaerial vehicle. For example, a first unmanned aerial vehicle iscontrolled by a client (a user name is ID_01) running on a controlterminal. After the first unmanned aerial vehicle flies for a pluralityof times, an obtained flight tag displayed in the client may be shown inFIG. 4. Takeoff geographic locations included in a first flight tag(represented by using “occupying for a first time”) are as follows:“Eiffel Tower, France (Sep. 24, 2015)”, “Madrid, Spain (Jul. 17, 2015)”,“Hokkaido, Japan (Jun. 4, 2015)”, and “Paradise Island, the Maldives(Apr. 30, 2015)”. Takeoff geographic locations included in a secondflight tag (represented by using “flying across”) are as follows:“Triumphal arch, France (Sep. 23, 2015)”, “Barcelona, Spain (Jul. 19,2015)”, and “Tokyo, Japan (Jun. 6, 2015)”.

Optionally, in this embodiment, the takeoff geographic location of theforegoing first unmanned aerial vehicle may include but is not limitedto one of the following: 1) a geographic location of the first unmannedaerial vehicle when the first unmanned aerial vehicle takes off; or 2) ageographic location of the control terminal when the first unmannedaerial vehicle takes off. When the takeoff geographic location of thefirst unmanned aerial vehicle is the geographic location of the firstunmanned aerial vehicle when the first unmanned aerial vehicle takesoff, the takeoff geographic location may be obtained in, but is notlimited to, at least one of the following manners: 1) The controlterminal obtains the geographic location of the first unmanned aerialvehicle collected by the first unmanned aerial vehicle when the firstunmanned aerial vehicle takes off; or 2) The control terminal obtains,by detection, the geographic location of the first unmanned aerialvehicle when the first unmanned aerial vehicle takes off.

Optionally, in this embodiment, the determining whether there is atakeoff geographic location in stored takeoff geographic locations thatis the same as the takeoff geographic location of the first unmannedaerial vehicle includes at least one of the following:

1) determining whether location information of the takeoff geographiclocation of the first unmanned aerial vehicle is consistent withlocation information of the stored takeoff geographic locations; or

2) determining whether region indication information in locationinformation of the takeoff geographic location of the first unmannedaerial vehicle is consistent with region indication information inlocation information of the stored takeoff geographic locations, theregion indication information being a part of the location information.

That is, a principle for determining a same takeoff geographic locationmay include but is not limited to at least one of the following: thelocation information is completely consistent, or the region indicationinformation (a part of the location information) used for indicating aregion in which the first unmanned aerial vehicle is located isconsistent.

Optionally, in this embodiment, that the first flight tag is sent to aclient includes: obtaining a geographic name corresponding to thetakeoff geographic location of the first unmanned aerial vehicle, andsending the first flight tag at least including the geographic name;that the second flight tag is sent to a client includes: obtaining ageographic name corresponding to the takeoff geographic location of thefirst unmanned aerial vehicle, storing a correspondence between thetakeoff geographic location of the first unmanned aerial vehicle and theobtained geographic name, and sending the second flight tag at leastincluding the geographic name.

Optionally, in this embodiment, the foregoing server may adjust, but isnot limited to, adjusting, according to the obtained takeoff geographiclocation of the unmanned aerial vehicle, the takeoff geographiclocations stored in the database of the server. Specifically, when thesecond flight tag used for indicating that the first unmanned aerialvehicle is an unmanned aerial vehicle first taking off from the takeoffgeographic location of the first unmanned aerial vehicle is obtained,the geographic name corresponding to the takeoff geographic location ofthe first unmanned aerial vehicle is obtained, and the correspondencebetween the takeoff geographic location of the first unmanned aerialvehicle and the obtained geographic name is stored, to newly add atakeoff geographic location to the database.

According to the embodiment provided in this embodiment, the serverobtains a corresponding flight tag according to the obtained takeoffgeographic location, and sends the flight tag to the client, so that theserver establishes a common database of unmanned aerial vehicles on theserver by using the obtained takeoff geographic location of the unmannedaerial vehicle. Further, interaction is established between the clientrunning on the control terminal and the server by using the database, toimplement sharing of the takeoff geographic location of the unmannedaerial vehicle, and return the flight tag corresponding to the unmannedaerial vehicle to the control terminal according to the takeoffgeographic location of the unmanned aerial vehicle. Therefore, theforegoing flight tag of the unmanned aerial vehicle can be shared insocial space of the client.

In an optional solution, the determining unit 904 includes at least oneof the following:

1) a first determining module, configured to determine whether locationinformation of the takeoff geographic location of the first unmannedaerial vehicle is consistent with location information of the storedtakeoff geographic locations; or

2) a second determining module, configured to determine whether regionindication information in location information of the takeoff geographiclocation of the first unmanned aerial vehicle is consistent with regionindication information in location information of the stored takeoffgeographic locations, the region indication information being a part ofthe location information.

That is, a principle for determining a same takeoff geographic locationmay include but is not limited to at least one of the following: thelocation information is completely consistent, or the region indicationinformation (a part of the location information) used for indicating aregion in which the first unmanned aerial vehicle is located isconsistent.

In an optional solution,

1) the first sending unit 906 includes a first sending module,configured to obtain a geographic name corresponding to the takeoffgeographic location of the first unmanned aerial vehicle, and send thefirst flight tag at least including the geographic name; and

2) the second sending unit 908 includes a second sending module,configured to obtain a geographic name corresponding to the takeoffgeographic location of the first unmanned aerial vehicle, store acorrespondence between the takeoff geographic location of the firstunmanned aerial vehicle and the obtained geographic name, and send thesecond flight tag at least including the geographic name.

Optionally, in this embodiment, the foregoing server may adjust, but isnot limited to, adjusting, according to the obtained takeoff geographiclocation of the unmanned aerial vehicle, the takeoff geographiclocations stored in the database of the server. Specifically, when thesecond flight tag used for indicating that the first unmanned aerialvehicle is an unmanned aerial vehicle first taking off from the takeoffgeographic location of the first unmanned aerial vehicle is obtained,the geographic name corresponding to the takeoff geographic location ofthe first unmanned aerial vehicle is obtained, and the correspondencebetween the takeoff geographic location of the first unmanned aerialvehicle and the obtained geographic name is stored, to newly add atakeoff geographic location to the database.

Embodiment 5

According to this embodiment of this application, a flight tag obtainingterminal configured to implement the foregoing flight tag obtainingmethod is further provided. As shown in FIG. 10, the terminal includes:

1) a processor (processing circuitry) 1002, configured to obtain atakeoff geographic location of a first unmanned aerial vehicle when thefirst unmanned aerial vehicle takes off;

2) a communications interface 1004, connected to the processor 1002, andconfigured to send the takeoff geographic location of the first unmannedaerial vehicle to a server; and obtain a flight tag returned by theserver, the flight tag being used for indicating whether the firstunmanned aerial vehicle is an unmanned aerial vehicle first taking offfrom the takeoff geographic location of the first unmanned aerialvehicle; and

3) a memory 1006, connected to the processor 1002 and the communicationsinterface 1004, and configured to store the takeoff geographic locationof the first unmanned aerial vehicle and the flight tag returned by theserver.

Optionally, for a specific example in this embodiment, refer to theexamples described in Embodiment 1 and Embodiment 2, and details are notdescribed herein again in this embodiment.

Embodiment 6

According to this embodiment of this application, a flight tag obtainingserver configured to implement the foregoing flight tag obtaining methodis further provided. As shown in FIG. 11, the server includes:

1) a communications interface 1102, configured to receive a takeoffgeographic location of a first unmanned aerial vehicle when the firstunmanned aerial vehicle takes off sent by a client, the client runningon a control terminal and being configured to control the takeoff of thefirst unmanned aerial vehicle;

2) a processor (e.g., processing circuitry) 1104, connected to thecommunications interface 1102, and configured to determine whether thereis a takeoff geographic location in stored takeoff geographic locationsthat is the same as the takeoff geographic location of the firstunmanned aerial vehicle; and if yes, send a first flight tag to theclient, the first flight tag being used for indicating that the firstunmanned aerial vehicle is not an unmanned aerial vehicle first takingoff from the takeoff geographic location of the first unmanned aerialvehicle; or if no, send a second flight tag to the client, the secondflight tag being used for indicating that the first unmanned aerialvehicle is an unmanned aerial vehicle first taking off from the takeoffgeographic location of the first unmanned aerial vehicle; and

3) a memory 1106, connected to the communications interface 1102 and theprocessor 1104, and configured to store the takeoff geographic locationof the first unmanned aerial vehicle and the flight tag returned by theserver.

Optionally, for a specific example in this embodiment, refer to theexamples described in Embodiment 1 and Embodiment 2, and details are notdescribed herein again in this embodiment.

Embodiment 7

According to this embodiment of this application, a storage medium isfurther provided. Optionally, in this embodiment, the storage medium isconfigured to store program code for performing the following steps:

S1: Obtain a takeoff geographic location of a first unmanned aerialvehicle when the first unmanned aerial vehicle takes off.

S2: Send the takeoff geographic location of the first unmanned aerialvehicle to a server.

S3: Obtain a flight tag returned by the server, the flight tag beingused for indicating whether the first unmanned aerial vehicle is anunmanned aerial vehicle first taking off from the takeoff geographiclocation of the first unmanned aerial vehicle.

Optionally, in this embodiment, the storage medium is further configuredto store program code for performing the following steps:

S1: Receive a takeoff geographic location of a first unmanned aerialvehicle when the first unmanned aerial vehicle takes off sent by aclient, the client running on a control terminal and being configured tocontrol the takeoff of the first unmanned aerial vehicle.

S2: Determine whether there is a takeoff geographic location in storedtakeoff geographic locations that is the same as the takeoff geographiclocation of the first unmanned aerial vehicle.

S3: If yes, send a first flight tag to the client, the first flight tagbeing used for indicating that the first unmanned aerial vehicle is notan unmanned aerial vehicle first taking off from the takeoff geographiclocation of the first unmanned aerial vehicle.

S4: If no, send a second flight tag to the client, the second flight tagbeing used for indicating that the first unmanned aerial vehicle is anunmanned aerial vehicle first taking off from the takeoff geographiclocation of the first unmanned aerial vehicle.

Optionally, in this embodiment, the storage medium may include but isnot limited to a non-transitory or transitory medium that may storeprogram code such as a USB flash drive, a read-only memory (ROM), arandom access memory (RAM), a removable hard disk, a magnetic disk, oran optical disc.

Optionally, for a specific example in this embodiment, refer to theexamples described in Embodiment 1 and Embodiment 2, and details are notdescribed herein again in this embodiment.

The sequence numbers of the preceding embodiments of this applicationare merely for description purpose but do not indicate the preference ofthe embodiments.

When the integrated unit in the foregoing embodiment is implemented in aform of a software functional unit and sold or used as an independentproduct, the integrated unit may be stored in the foregoingcomputer-readable storage medium. Based on such an understanding, thetechnical solutions of this application essentially, or the partcontributing to the existing technology, or all or some of the technicalsolutions may be implemented in a form of a software product. Thecomputer software product is stored in a storage medium and includesinstructions for instructing one or more computer devices (which may bea personal computer, a server, or a network device) to perform all orsome of the steps of the methods in the embodiments of this application.

In the foregoing embodiments of this application, descriptions of theembodiments have different emphases, and for parts that are notdescribed in detail in one embodiment, refer to the related descriptionsof the other embodiments.

In the several embodiments provided in this application, it should beunderstood that the disclosed client may be implemented in othermanners. The described apparatus embodiments are merely exemplary. Forexample, the unit division is merely logical function division and maybe other division during actual implementation. For example, a pluralityof units or components may be combined or integrated into anothersystem, or some features may be ignored or not performed. In addition,the displayed or discussed mutual couplings or direct couplings orcommunication connections may be implemented by using some interfaces.The indirect couplings or communication connections between the units ormodules may be implemented in electronic or other forms.

The units described as separate parts may or may not be physicallyseparate, and parts displayed as units may or may not be physical units,may be located in one position, or may be distributed on a plurality ofnetwork units. Some or all of the units may be selected according toactual needs to achieve the objectives of the solutions of theembodiments.

In addition, functional units in the embodiments of this application maybe integrated into one processing unit, or each of the units may existalone physically, or two or more units are integrated into one unit. Theintegrated unit may be implemented in a form of hardware, or may beimplemented in a form of a software functional unit.

The above descriptions are merely exemplary embodiments of thisapplication, and it should be noted that, persons of ordinary skill inthe art may make various improvements and refinements without departingfrom the spirit of this application. All such modifications andrefinements should also be intended to be covered by this application.

What is claimed is:
 1. A non-transitory computer-readable medium storinginstructions which when executed by at least one processor cause the atleast one processor to perform operations comprising: obtaining, by theat least one processor of an information processing apparatus, a firsttakeoff geographic location of a first unmanned aerial vehicle when thefirst unmanned aerial vehicle takes off from the first takeoffgeographic location, the information processing apparatus executing anapplication controlling the first unmanned aerial vehicle; sending, bythe at least one processor of the information processing apparatus, thefirst takeoff geographic location of the first unmanned aerial vehicleto a server; receiving a first flight tag from the server, the firstflight tag indicating whether another unmanned aerial vehicle took offfrom the first takeoff geographic location of the first unmanned aerialvehicle before the first unmanned aerial vehicle took off from the firsttake off geographic location, based on data recorded in a database; anddisplaying the flight tag in the application executed by the informationprocessing apparatus, the flight tag indicating a first geographic namecorresponding to the first takeoff geographic location of the firstunmanned aerial vehicle.
 2. The non-transitory computer-readable mediumaccording to claim 1, wherein the sending comprises: when the firstunmanned aerial vehicle takes off, sending the first takeoff geographiclocation of the first unmanned aerial vehicle to the server; or afterthe first unmanned aerial vehicle takes off, sending the first takeoffgeographic location of the first unmanned aerial vehicle to the server.3. The non-transitory computer-readable medium according to claim 1,wherein the sending comprises: after the first unmanned aerial vehicletakes off, obtaining a sending instruction, and sending, in response tothe sending instruction, the first takeoff geographic location of thefirst unmanned aerial vehicle to the server; or after the first unmannedaerial vehicle takes off, determining whether a preset sending moment isreached, and based on a determination that the preset sending moment isreached, sending the first takeoff geographic location of the firstunmanned aerial vehicle to the server.
 4. The non-transitorycomputer-readable medium according to claim 3, wherein the obtaining thesending instruction comprises: receiving a user selection of apredetermined trigger button, collecting a predetermined voice, orobtaining a predetermined motion gesture.
 5. The non-transitorycomputer-readable medium according to claim 3, wherein the presetsending moment is a moment that satisfies a predetermined condition or apreset cycle end moment.
 6. The non-transitory computer-readable mediumaccording to claim 1, wherein the obtained first takeoff geographiclocation of the first unmanned aerial vehicle is a geographic locationof the first unmanned aerial vehicle when the first unmanned aerialvehicle takes off.
 7. The non-transitory computer-readable mediumaccording to claim 6, wherein the first geographic location of the firstunmanned aerial vehicle when the first unmanned aerial vehicle takes offis collected by the first unmanned aerial vehicle and provided to theinformation processing apparatus.
 8. The non-transitorycomputer-readable medium according to claim 6, wherein the firstgeographic location of the first unmanned aerial vehicle when the firstunmanned aerial vehicle takes off is detected by the informationprocessing apparatus.
 9. The non-transitory computer-readable mediumaccording to claim 1, wherein the obtained first takeoff geographiclocation of the first unmanned aerial vehicle is a geographic locationof the information processing apparatus that controls the takeoff of thefirst unmanned aerial vehicle.
 10. The non-transitory computer-readablemedium according to claim 1, wherein the displaying comprises: when thefirst flight tag indicates no other unmanned aerial vehicle took offfrom the first takeoff geographic location of the first unmanned aerialvehicle before the first unmanned aerial vehicle took off from the firstgeographic location, displaying the first geographic name correspondingto the first takeoff geographic location of the first unmanned aerialvehicle on a list in the application executed by the informationprocessing apparatus, the list including second geographic names eachcorresponding to a second flight tag received from the server indicatingno other unmanned aerial vehicle took off from a second takeoffgeographic location corresponding to the respective second geographicname before the first unmanned aerial vehicle.
 11. A method, comprising:obtaining, by circuitry of an information processing apparatus, a firsttakeoff geographic location of a first unmanned aerial vehicle when thefirst unmanned aerial vehicle takes off from the first takeoffgeographic location, the information processing apparatus executing anapplication controlling the first unmanned aerial vehicle; sending, bythe circuitry of the information processing apparatus, the first takeoffgeographic location of the first unmanned aerial vehicle to a server;receiving a first flight tag from the server, the first flight tagindicating whether another unmanned aerial vehicle took off from thefirst takeoff geographic location of the first unmanned aerial vehiclebefore the first unmanned aerial vehicle took off from the first takeoff geographic location, based on data recorded in a database; anddisplaying the flight tag in the application executed in the informationprocessing apparatus, the flight tag indicating a first geographic namecorresponding to the first takeoff geographic location of the firstunmanned aerial vehicle.
 12. The method according to claim 11, whereinthe sending comprises: when the first unmanned aerial vehicle takes off,sending the first takeoff geographic location of the first unmannedaerial vehicle to the server; or after the first unmanned aerial vehicletakes off, sending the first takeoff geographic location of the firstunmanned aerial vehicle to the server.
 13. The method according to claim11, wherein the sending comprises: after the first unmanned aerialvehicle takes off, obtaining a sending instruction, and sending, inresponse to the sending instruction, the first takeoff geographiclocation of the first unmanned aerial vehicle to the server; or afterthe first unmanned aerial vehicle takes off, determining whether apreset sending moment is reached, and based on a determination that thepreset sending moment is reached, sending the first takeoff geographiclocation of the first unmanned aerial vehicle to the server.
 14. Themethod according to claim 13, wherein the obtaining the sendinginstruction comprises: receiving a user selection of a predeterminedtrigger button, collecting a predetermined voice, or obtaining apredetermined motion gesture.
 15. The method according to claim 13,wherein the preset sending moment is a moment that satisfies apredetermined condition or a preset cycle end moment.
 16. The methodaccording to claim 11, wherein the obtained first takeoff geographiclocation of the first unmanned aerial vehicle is a geographic locationof the first unmanned aerial vehicle when the first unmanned aerialvehicle takes off.
 17. The method according to claim 16, wherein thefirst geographic location of the first unmanned aerial vehicle when thefirst unmanned aerial vehicle takes off is collected by the firstunmanned aerial vehicle and provided to the information processingapparatus.
 18. The method according to claim 11, wherein the obtainedfirst takeoff geographic location of the first unmanned aerial vehicleis a geographic location of the information processing apparatus thatcontrols the takeoff of the first unmanned aerial vehicle.
 19. Themethod according to claim 11, wherein the displaying comprises: when thefirst flight tag indicates no other unmanned aerial vehicle took offfrom the first takeoff geographic location of the first unmanned aerialvehicle before the first unmanned aerial vehicle took off from the firstgeographic location, displaying the first geographic name correspondingto the first takeoff geographic location of the first unmanned aerialvehicle on a list in the application executed by the informationprocessing apparatus, the list including second geographic names eachcorresponding to a second flight tag received from the server indicatingno other unmanned aerial vehicle took off from a second takeoffgeographic location corresponding to the respective second geographicname before the first unmanned aerial vehicle.
 20. An apparatus,comprising circuitry configured to: obtain a first takeoff geographiclocation of a first unmanned aerial vehicle when the first unmannedaerial vehicle takes off from the first takeoff geographic location viaan application controlling the first unmanned aerial vehicle; send thefirst takeoff geographic location of the first unmanned aerial vehicleto a server; receive a first flight tag from the server, the firstflight tag indicating whether another unmanned aerial vehicle took offfrom the first takeoff geographic location of the first unmanned aerialvehicle before the first unmanned aerial vehicle took off from the firsttake off geographic location, based on data recorded in a database; anddisplay the flight tag in the application controlling the first unmannedaerial vehicle, the flight tag indicating a first geographic namecorresponding to the first takeoff geographic location of the firstunmanned aerial vehicle.